My guess is that the query is doing a bookmark lookup. When the server
isn't busy, MSSQL is trying to be helpful by issuing read-aheads
against the clustered index. I would try creating a covering index, so
MSSQL will only have to read one index.