I was thinking we could an expansion of the macro using other config constants plus sizeof's (assuming we can access them from other code) and maybe add a few percent for contingency.  If we can't access the appropriate sizeofs then the ideal solution would be to add APIs that can be called to get the memory requirements for each resource.

This may all be too much effort, but I'm nervous of just having very large increment.