precise versions may be overwritten with `--recursive=true` (default)

[epage]

With #790 being fixed with #795, there are "last writer win" issues where one cargo update --aggressive might do the precise version selection from a previous cargo update.

I assume we can fix this when integrating cargo upgrade into cargo by adjusting the internal API for cargo update to meet our need (multiple precise being set and some non-precise being set)