"Is there any way to avoid this and to force allocation in the creation stage of the application?"
By reinventing TBB, perhaps?
Have you tried its scalable allocator (which lives up to its name), and, if you're not satisfied that it suits your purpose, what are you trying to achieve?
There are cases where dynamic allocations are prohibited. One example is the Joint Strike Airforce C++ coding standard which prohibits dynamic allocations,
But this is quite extreme. Few"normal" applications really benefit from this kind of rigidity,especially not if you're using a standard operating system like Windows, Linux, Mac OS X, Solaris, AIX or HP-UX.
So either your application is very extreme or you're avoiding dynamic allocations for more esoteric reasons: Like you've heard that dynamic allocations are slow and should be avoided. Or even that you feel dynamic allocations are hard to get right so you rather avoid them.
In any case it would be interesting to know why you're shying away from dynamic allocations. I can tell you right away that toaltogether avoid dynamic allocations on the standard OS:es I mentioned is close to impossible. What you could reasonably settle for is to not make any dynamic allocations yourself. And if you adopt thatthat approach you can use TBB without problems:)