XsdObjectGen.ex vs Xsd.exe for .NET 2.0 usage

[Jeff Killberg]

I am working on a .NET 2.0 project where we will be defining a large object
model in XML schema and generating the C# code to process XML documents
conforming to this XML schema into the object model.

On a similar project, we used XsdObjectGen.exe. I am trying to determine if
there are major enough reasons to use XsdObjectGen or if the .NET 2.0 version
of Xsd.exe will suffice.

Our XML schema will be defined using a fairly minimal set of schema
conventions:
- we will be creating named, complex types that make use of a limited set of
primitive types (string, integer, decimal, date and dateTime)
- the only model group we are using is sequence
- we are essentially making use of the Venetian Blind design pattern
- we will not be using substitution groups
- we will be using type derivation

Are there any major differences that would make me want to use one tool over
the other?
One feature in XsdObjectGen that did look enticing was the support for
creating Collections for repeated elements rather than needing to deal with
Array-style code constructs.

Thanks in advance for your comments!
Jeff