logical reads [and writes, CPU, duration] will be aggregated during your user session
- when you logout you get these totals [they are not for the actual logout itself!]
in your example the db engine has done 1M reads (hopefully mostly from cached blocks in memory), which probably means little
- what you need is to look at each statement-end to see where the big numbers are
suggest you get the Ben-Gan TSQL Querying book (chapter3 if I remember as mine has gone walkies) which tells you how to boil down a huge Profiler capture into distinct statements
- you can discover which are the heavy hitters
or use the SSMS report "top queries by total IO" [context menu on the instance] to see this
HTH
Dick