Some of them are:
1) are auto-freeing templatized heap object class (the compiler will automatically call destructor when objects goes out of scope, call free in the destructor).
2) Overload free/delete to fill up freed memory with 0xdeadbeef etc so that code that reads from there is likely to crash due to invalid data.
3) Use one of the non-libc memory managers which will track memory allocs and frees and tell at exit if all memory was freed. Some will even have tricks to tell you which allocation was not freed.
4) If all else fails, use Valgrind for the really tough ones.
Coupled with a good regression/unit test suite, memory leak tracking will be an insignificant part of your development effort.