Hi Phil,
Is this a real life example of how you are going to handle reports? Meaning what is the point of doing this test? I don't see any kind of counter so not clear how exactly how you are doing it...
Try adding in some delay between loads, it could be you need to let the OS catch up. There are known memory leaks, majority of them are in Windows dll's, a simple test like this typically will show CR has about a 6k leak. Windows has Meg's of leaks.
If you are going to do report bursting like this then create a threading app and load each report in it's own process, when the process is closed or killed it will release the memory as well.
And you will run into limitations. CR for VS allows 3 reports to be loaded at one time and that is it. For high volume report processing you should go to CRSE ( OEM) or CR Server for more RAS servers limited to one PC then to BI 4.1 which you can specify the number of RAS Server based on CPU's and add more PC's to add more RAS Servers. They run as a service, you can then add more RAS Servers according to your loads.
Don