Did you ever find an answer to this? I have a similar situation: I have a query that consistently showing 2.4 million reads in profiler, yet running the exact same query in SSMS results in the following
Table 'X'. Scan count 1, logical reads 13, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
The execution shows a 100% nonclustered index seek...so not really sure what can be done to "optimize".
In addition, in profiler the duration is always around 2.561 seconds, yet running via SSMS is constently < 1sec.
______________________________________________________________________________"Never argue with an idiot; They'll drag you down to their level and beat you with experience"