You're probably not the only one, but that doesn't mean that the set of people who think it's a terrible idea are any less misguided or wrong. This is normal and standard and most tools for tracking versions assume version numbers work this way. Including the tools that do dynamic linking at run-time for you. In fact, for libraries, it's mandatory to do this if you have more than ten backwards-compatible releases in a series. A change in the second number of a library's version indicates that it's backwards-compatible but not forwards-compatible. (Forwards-compatible changes get a change in the third digit; incompatible changes get a change in the first.)
The only people likely to be confused to the degree that you suggest are non-technical idiots in the commercial press, and they'll make illiterate mistakes about all sorts of things no matter what we do. Hundreds of thousands of software projects do this sort of thing regularly (as AC pointed out, linux v. 1.1.10 was released in 1994). It's "three dot ten", not "three point one zero". Version numbers aren't decimals.
Of course, a lot of projects make sure to always list all three numbers (e.g. 3.10.0). Which I admit I prefer. But it's still the start of the 3.10 series.