This is pretty simple actually! At startup, create some object pools, arenas, or bump allocators. Then, never heap allocate anything ever. We also happen to do

This is pretty simple actually! At startup, create some object pools, arenas, or bump allocators. Then, never heap allocate anything ever. We also happen to do 0 other steady-state syscalls (not just 0 mmap, munmap, mremap, etc.), so we can just run the program under valgrind and any time valgrind prints something is a bug. We didn't use C++ but some other software I've heard uses a similar approach is written in C++.