I believe my original implementation used just the System.Data.Oracle provider, but I was using Regular expressions to parse out the information from the packages (because I falsely believed that that information would not be available from the provider based on my experiences working with ADOX and OLEDB providers from several vendors).
Roelof Blom (sp?) stripped out my regular expressions (ultimately a good thing), and added the System.Data.OleDb namespace into the mix because (as I understand it) a overflow exception problem when dealing with the FLOAT data type. I honestly have not inspected the changes he made too closely, but I do know that maybe a fresh start would not be a bad idea. However, I would encourage you to create a table that uses a FLOAT type and report back what you experience... and maybe look through the posts of the original thread to make sure I'm remember right why he added the OleDB to the mix.
I actually implemented the extended properties today based on the table layout listed in my earlier post. I'm supporting 4 basic data types initially... System.Int32, System.Double, System.DateTime, and System.String. It's a bit hacked up, but I wanted to get things rolling with it and get on with my real work.