I have been using my own global memory management routines and overriding the new and delete operators in my engine for some time now, and the system seems to work pretty well for me. I develop games for several platforms including DS and IPhone, so it's nice have full control over how much memory is available, how it is allocated and so on, even when developing on PC. Unfortunately, because my memory manager in initialised in the main entry point (WinMain or whatever the platform equivalent might be) any attempts to allocate memory at the static initialisation stage are doomed to failure (or worse). Here's a quick example: Does anyone know of a good way for me to initialise my memory manager before static initialisation occurs? If not do you have other suggestions as to how I might get round this problem? Thanks in advance.

Thanks bobofjoe, that's exactly what I was after, I'll give it a go and see if I can find equivalent pragmas for other platforms.
Personally I try to avoid static initialisation, and like you say it is the only truly platform independant solution, but I work in a team and I'd rather avoid imposing such limitations... everyone has their own way of doing things.