Vector.equals uses iterators. Could be optimised

[mkeskells]

If a Vector is compared to another Vector (or some other collection that efficiently implements length and apply) then we should prefer that mechanism, with a default/fallback to the existing iterator mechanism

This issue was inspired by an observed issue in a production application

We should include a benchmark in any fix