How does that deal with stack-allocated data that gets twiddled by some other code expecting that it will be able to do so, where that expectation outlives the actual stackframe itself?
Apparently many forget C was on that role as well.
> At some level they all rely on massive libraries written in C
What? How does your "C++ product [that] does not use a single explicit allocation" actually manage memory?