Use UCFS to avoid ambiguous method calls

Very cool crate - I like the concept very much! When I have two traits in scope that share a method name, I get error[E0034]: multiple applicable items in scope. My hunch is that this should be solved by emitting UFCS calls, as suggested by the compiler, e.g.: "help: to disambiguate the method call, write std::iter::ExactSizeIterator::len(&inner) instead"

Does that seem plausible? I'm happy to try and fix this and send you a PR if that would be helpful.

Thanks!