I have an assembly with the following manifest embedded:
After struggling with the same problem, I have noticed that the updates applied to development Visual Studio installation might address some target machine updates:
For example, the highlighted update above addresses this specific question.
Instaed of relaying on side by side I would suggest you to don't include the "Manifest file" inside your assembly. Expecially because you cannot be sure that the PC you're going to install your software is updated to the version included in your manifest.
You can disable it setting the project property "Linker\Manifest File\Generate Manifest" to "No".
I hope this could help. Good luck
Sorted!
Someone kindly pointed out to me that the '"SomeAssembly.dll"' mentioned in Dependency Walker was in fact a different dll from the one I opened in Dependency Walker! (Whoops!)
Looking at the manifest for this assembly I can see that the problem is due to the fact that Microsoft.VC80.CRT v8.0.50727.4053 is targetted, but not present on this machine. (Installed via a security update).