Lazy loading can be avoided by specifying a reference or collection field as belonging to the default fetch group. However, why would you do this? This is a compile time setting, and using FetchPlans is much more flexible at runtime.
Just to clarify this: Because a reference or collection is loaded lazily this does not mean that the user visible instance of the collection is filled with null; it just means that it is fetched from the database when it is acutally needed. Because our enhancer allows to detect field accesses on persistent classes we can do late fetches when the reference / collection field content is actually requested by the application. Lazy loading will then fetch the data from the server; eager loading will have the data fetched already when the surrounding object is fetched and reuse the data that is already present in the client. In both cases a reference or collection instance will be returned upon field access.
the Telerik team
Q3'12 SP1 of OpenAccess ORM packs Multi-Table Entities mapping support. Check it out.