If you file some issues I can make sure the move-ctor bug is fixed, as well as the const iterator.
I've been thinking about lifting the copy-constructor restriction in AMTL. It'd require an opt-in parameter:
ke::Vector v2(v1, ke::ExplicitCopy());
Unfortunately that wouldn't fix a separate issue, which is that you can't capture these things by-value in lambdas, which is really annoying. Sometimes you know the contents is small enough to copy and you don't care about the performance.