I have probably been overstating my point (sorry!), but for me, it boils down to a couple things:

1) Syntactically, I much prefer C#. This is 100% opinion and probably meaningless, but IMO you can tell C# was designed recently with a strong emphasis on combining the best features of many languages. VB.Net feels very much like they crammed an old language paradigm onto a new technology stack. (Little things, like the way For loops are constructed in VB, drive me nuts!)
Well i don't disagree i much prefer the C# syntax i like its terseness and when i switch between one and the other (for work) it is always when i am in a VB.Net project that i end up writing C# by accident rather than the other way round!

Saying that i am not sure that makes it a better language or not!

2) The unsafe keyword is extremely useful in my line of work, so for me, that's a major loss in VB.Net.
Aha Pointers, so if you end up using unmanaged C++ dll's in your projects then of course you must use C# over VB.NET.

3) 3rd-party libraries was the wrong wording, I think. My apologies. I was lumping that in with "code samples", e.g. "open-source libraries", not compiled libraries. One need only compare the number of source code lines available at an open-source aggregator like OpenHub:

C# open-source projects: 871,129,246 lines of code
VB open-source projects: 49,205,300 lines of code

Not only is there 20x more C# code out there, the VB total includes both VB.Net and VB6. Pretty sad.
Yes although i wonder sometimes if there is a bit of snobbery at play here. VB still has an image problem amongst some coders, and C# is just seen as cooler particularly in the open source community

Again i am not sure that makes it a better language.

4) On average, C# jobs pay some $5k more than VB jobs, at least in the U.S. If you can switch between both languages with ease, that's awesome and the best way to go. But C# skills seem to be valued more highly.
Hmm i would tend to agree in the UK on the whole its similar, but once again i don't see how this make it a better language

5) All the new toys come to C# first. You can tell it's the first-class .NET citizen (as it should be, IMO, given all the numbers above). While VB.Net eventually gains most those features, if you can use both languages, I just don't see any reason to go with VB.Net over C#.
The Framework is fairly mature now, most new features have arrived and are in both languages. I agree that this definitively used to be a big thing, however i am not sure it is anymore!

So summing up Apart from Pointers (unsafe code - which is one of the true differences between the languages) most of your points seem to be about the development community around the language and which is the best for jobs.

Both of these are valid points and i would even say they will guide some people when making decisions on what to use, however i am not convinced we should be saying the C# is superior just as a language to VB.Net.

Its all the stuff that comes with it that makes me prefer C#, and your first point, i personally just prefer the syntax!

Saying that there are some talented VB.Net programmers on this forum who can do anything i could do with C# in VB and as they prefer the VB Syntax i don't think they should be looked down on