>It should not be necessary to issue GO BOTTOM / GO TOP after each seek.

What about picking two or more existing keys from the table and cycling the seek()/indexseek() between those values? That should give a more realistic picture than artificially moving the record pointer in each loop iteration (especially as _not_ moving the record pointer is indexseek()'s forte).