This. Absolutely this.

Bear in mind that nolock doesn't just mean dirty reads. Keeping nolock may seem fine until that one day where data is changing and the nolock hint allows a report to read a few rows multiple times. Nothing tends to annoy users more than results that are incorrect, except business decisions made off that incorrect data (eg if it's financial data duplicate/missed row may result in an account total showing too high or too low, resulting in the business approving/denying transactions incorrectly)