It's impossible to memory leak even with bugs if you don't use antique parts of the language that won't pass any static analysis anyways.
https://github.com/search?q=repo%3Achromium%2Fchromium+memor...
A few leaks fixed per month is nothing. Further there is no major language promising no leaks once you include things like retained references to garbage and reference cycles. Leaks are one thing modern C++ solves pretty well.
It's not indicative of anything average in the real world.
class A {};
std::unique_ptr<A> array(new A[256]);
It's very easy to produce innocuous-looking code that contains leaks. (And yes, I know that make_unique solves the problem here.)