Aaron,

I don't think newobject is really the solution. Steve Black has posted code that he uses to benchmark object instantiation time, destruction time and memory footprint size and it creates several thousands of objects.

I'd suspect your clean up code isn't quite cleaning up everything it needs to.

>The objects aren't that complex, bascially it just opens some tables, adjusts them or returns calculations based on their content, then cleans up after itself.
>
>I'm going to try Glen's idea of using NEWOBJECT instead as I can bypass the loss of the CLASSLIB setting by specifying the class as a parameter, I'll let you know how it goes one way or the other.