IRenderable: like I said, pretty minimal changes... we use a couple templated classes, but operator overloading is not an accepted practice. Other Office teams have more fully embraced C++ (e.g. Powerpoint and IGX) with common use of smart pointers, OO code, etc.
nektar: you will retain your text content in the PDF. We don't convert it to a big picture. We use several IDEs, it's just personal preference - VS, SlickEdit, Codewright, and Source Insight are common. Source control, testing, and bug tracking are all handled with internally developed tools.
guru: filesize is something that's been looked at closely and improved since Beta 1. As far as quality, I'm not sure what kind of documents you're publishing, but do make use of the Beta 1 reporting tools, we look at everyone's feedback.
Dwight: if you give me your contact info, I'll pass it on to any interested parties.