if you used the clone just delete them and re-clone or delete the folder and copy the latest over.

Use the library manager to install the correct version before doing so, that way your documents/arduino/libraries will have also have the same version, then clone or copy that.

Make sense?

If you originally copied your library to the project libraries folder then you should continue to do same because the code could have come from anywhere.

If you use the git source control or tfs option in visual studio to manage your source it will automatically handle versioning for you allowing you to review all preview changes simply by right clicking files in the solution explore > view history or > compare etc.

If you use clone then it is easy. Install the new library with Library Manager, clone the new library then remove the "Reference" from the Arduino project to the cloned library you no longer use.

The clone automatically uses the version of the library when cloning, therefore the older version can remain. You can organize the libraries in the solution explorer to clearly show the version numbers of same libraries. The "References" folder below the Arduino project in solution explorer gives you control over which of the various library version you actually want to use.

Sorry I am not sure I understand what you are asking.

There are no paths to headers in your .ino code, which ever library is set as the Project>Reference is the one that will be used during compilation. You can have multiple versions of the same library in the solution.

Does this answer your question?

I see, it should only add #includes if they are missing or different. Were the existing ones identitical?

That is correct. It is how things work for Arduino. You can remove the ones you don't want. The alternative would be not to add any headers which would be very confusing. Often there is not a header that matches the name of the library, therefore it would more problematic for users who don't know what header(s) to include or what a header is.

Hopefully, you are saying that you can now see how to easily support multiple versioned libraries and use the preffered one at any one time?

Great. If the library.properties does not contain an includes= we add all headers, that can't be switched off but an "Undo" in the .ino code should remove them if they have just beedn added.

If the library.properties contains one of more comma seperated .h names then only those .h files are automatically added to the code when adding libraries.

library.properties

includes=file1.h,file2.h

Great thanks for the update