BTW,
Gen17 has the exact same issue and here the docs point out;
// sounds better not going to extremes
drive.gain( 0.99 );
Which makes me believe this was known, maybe even intentional, however no mention is made of the differing behaviour between the UGen based scanning and code-based indexing and I'm not sure I see the use. Here it gets a bit mysterious to me.
Yours,
Kas.