Thanks John. Parsing is always a problem! 
I'm always getting system to stop parsing, regardless of where my contract happens to be. Usually I see a 1:1 (or worse) execute:parse ratio even when the SQL in question has bind variables. Go figure!
Java is the worst offender. I think because the SQL is a local variable in a member function, and as such, is created on the stack at runtime, parsed, bound (binded?), executed, fetched and then closed each time the function is called and goes (back) out of scope.
Cheers,
Norm. [TeamT]