We seem to have hit a glass ceiling with NCover on our build process. We run NCover on all builds to ensure that coverage does not fall (thanks to NCoverCop). In the last couple of days we have started to get out of memory exceptions. It seems that the process of generating a coverage report just takes too much memory.
The project is significant but not large (yet) so this was a surprise. The solution seems to be to break up the coverage test into multiple build tasks.