CreateObject microbenchmark optimizations

[manodasanW]

I did a benchmark against some scenarios which end up calling our CreateObject code path multiple times. Based on what I saw there, did some microbenchmark optimizations as this is a core code path used many times where costs can add up. In addition, I ran the rosyln code analyzer and did any changes that looked like it can impact perf or memory.

• Updating benchmark project versions and getting it working again for .NET native
• Every CreateObject calls ends up creating a couple of IObjectReference objects based on QIs and so on. Made some changes to avoid some unnecessary ones.
• The .GUID calls kept showing up on the ETW traces as being some cost as they look to use GetCustomAttributes internally. Hard coded the GUID of some of the ones we use in WinRT.Runtime. The IID optimizer could also help in some of these scnarios once we enable it for WinRT.Runtime, but these particular ones wouldn't really get optimized as .As or .TryAs were the ones doing the GetIID call.
• Made changes to allow for inlining of some exception functions which are called frequently
• Moved dispose func to local functions as it avoids a heap allocation for the func and was recommended by the rosyln analyzer

[Scottj1s]

looks good, subject to new Guid(...)