And, in a really busy environment, your No Lock query could say there's table corruption when there really isn't. I cannot remember the exact cause but it's to do with the nolock allowing another query to change the linked pages, etc and then when the nolock query comes across that bit it doesn't necessarily see the change straight away.

Run your DB with nolock to see how it goes. If need be you should probably change the transaction isolation level rather than explicitly specifying locking hints.