Well, it's also waste of time and if your app is constantly allocating and deallocating stuff it would take a lot more.
(I can count the times I did either of these on one hand, but of course this depends a lot on the code your working on).
Soon: programs implement their own allocators and memory pools and stop using the libc malloc, and thus stop benefiting from all the safety valves added to the libc malloc (including TFA), all because of the rumor that the libc malloc is slow (when it likely isn't).
Actually, that happened a couple decades ago.