If I say I tested with 20000 iterations, then i really tested with that amount. There is no reason for talking big, it's not about the most performant application But the number of iterations can give a clue about possible memory (or thread) leaks. If you can get just 100 iterations and someone else can easily perform 5000 you definitely have an issue.
Today I ran some tests with just the read-method (using the snippet a few posts back): on a WinXP machine I could easily increase the counter to 100k, but on a Win7 machine I got an OutOfMemoryError (unable to create new native thread) after about 10k threads, so it's definitely an OS issue. But again if you manage to have 500 iterations and someone else can run 3000 iterations, you might have a memory and/or thread leak.