There's a number of reasons for developing these:
1) We've (currently) got no way of tracking new/delete operations
2) We're using more and more C++ constructs in FSO, and we've noticed that occasionally someone has used malloc followed by memset(0) on an object containing a vector or other construct which initialises to a non-zero state
3) There is now the possibility of implementing and creating different allocator styles. We're experimenting with an O(1) allocator, pool allocators and other types of allocators for regularly used objects
4) We'll have a complete call stack for allocated objects (not currently implemented - that's tracking, not allocation)
We're aiming for performance improvements, code quality improvements and debugging improvements.
Aardwolf: It's not that it's bad, it's that it isn't trackable in FSO at present

Also, it's weakly linked, so the way we do it is possible (you can overload it in some quite interesting ways)
Also, this is not a unit test, this is a compile test. We're hoping people will play with it a little, and hopefully trip it up in ways that we haven't been able to imagine.