>What I had in mind was a 2-level nested scan that involved 2 different tables. The example you have given involves just one table which apparently causes the skipping that you speak of.

I am certainly not aware of any problems with nested scans. We have been using nested scans with two (or more) scans and tables for years without any trouble.