MS or Oracle OLEDB Provider?

MS Provider:
-No OS/NT Authentication
-NO stored procedures support

Oracle Provider:
-Both User AND OS/NT Authentication
-A bit faster
-stored procedures support
-Have to redistribute it with our app (only negative I can think of)

I"m going with Oracle's OLEDB provider. Thoughts? Experience with either that might shed some more light on the topic?

No experience with Oracle, but I would think the people who wrote the database would have the best access to the "good" functions to use in an OLEDB provider...just a thought.