Why, at least for as long as there's no complete garbage collector, isn't Max tracking allocations and spit out a list of those not referenced after the application was run in debug mode. It's dead simple to implement and pretty effective for tracking most leaks and it ususally doesn't need any noticable resources - and even if it would it wouldn't harm as it should obviously be optional / debug only.
Another maybe even better way would be to add user definable callbacks/notification for allocation events (alloc, free, add/remove ref, relocate - if the memory manager supports it) - so it would be even possible to easily create runtime memory monitors, track only relevant events etc.
Another maybe even better way would be to add user definable callbacks/notification for allocation events (alloc, free, add/remove ref, relocate - if the memory manager supports it) - so it would be even possible to easily create runtime memory monitors, track only relevant events etc.