Something I would preferably like to see go when testing is that the test code itself is consuming memory, in my Peter's (Race) Pacer project I can't run tests for the 16k watches as I'm getting an out of memory error due to the memory size the test code itself is taking.
If it can't be avoided having test code consume memory, then an easy solution would be to not impose a memory limit at all when in unit-test modus.
