I think Anchor Modeling would be brilliant for persisting objects. It is object-oriented by nature and has the flexibility and extensibility mechanisms necessary to cope with class changes. It also has a well defined XML definition, so I imagine only a very thin layer on the "programming language" side is necessary.
That being said, we have unfortunately not yet had the time to look into it. Although very interesting, an object to AM mapping is not currently on the top of the priority list. I think that in order to get such development started anytime soon we would need help from others. Feel like helping out? ;)
As Anchor Modeling is so very different from most other modeling techniques the best approach may be to roll our own ORM solution, rather than plugging in to existing ones. They are probably burdened by a lot of issues that are not present in Anchor Modeling. However, I don't know enough about Linq and Hibernate to be sure.