Just skimmed over the ORM class. I like it. I'll see if I can put it to use in my own projects, and if so, I'll likely contribute back to the project in the future. Of course, you will be respectfully credited.

It's a nice idea and useful for the most extreme simplistic cases. But I think there's room for more flexibility while still keeping it simple. For example, storing your db resource statically limits you to one database instance. And from what I skimmed, it looks like you can only update tables that have an autogenerated identity column, which leaves some tables and many updateable views out of the loop. Making slight changes in those departments would be a huge boost to flexibility.