Stop supposing that. I can almost guarantee that they are not because they are causing long term locks that are bugging you. You can't actually avoid locks. You just need to write good fast code. If you have long term locks, you don't have good fast code.
I was hit with such a problem this last week. Everyone said that a certain front-end related stored procedure was "already optimized" and could not be made faster because of the weird requirements. It took 1 CPU second to execute and used 227,000 reads per run and ran 26,500 times in an 8 hour period. I'd do the math for you... that's 7.36 hours of CPU time and more than 49 Tera Bytes of memory IO.
When I got done with it, the total CPU time used in 8 hours had been reduce to 13.25 CPU seconds as a total for all 26,500 runs and the number of bytes of memory IO had been reduced to only 13 Billion per day (3 orders of magnitude improvement on CPU and Reads).
If you're having problems with locks, look to your code because that's where the performance is. You can't get that kind of improvement even with SSDs or SnapShot Isolation.