Check the CMSDependencies folder
You could also try mapping the older version calls to the newer version and see if that helps you find the offending assembly - add the following to the configuration element in your web.config:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="CMS.Core" culture="neutral" publicKeyToken="834b12a258f213f9" />
<bindingRedirect oldVersion="0.0.0.0-9.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>