I usually run into this kind of thing when my developers take a standard object class, like a swfEdit, then wrap some homegrown functionality around the it which ends up making their own unique object class that (obviously) is not supported by QTP. Often I can manually resolve it by learning the object by hand (don't record, just add the object to the OR by hand and make sure to fiddle with the recognition properties until QTP can recognize the object. Sometimes I resolve it by treating it like a similar object (if swfEdit doesn't work, maybe webEdit might, etc.). Sometimes I work with the developers to see if they can revert it to be more like the original object (usually they won't do that but occasionally I get lucky). The rest of the time, I end up creating a virtual object and mapping it to the desired object, e.g. swfEdit, so that as far as QTP cares, it exposes all the events, properties, and methods of the object it's supposed to be.
If all else fails, you might find the combo object works best as three objects, a swfEdit, a swfButton, and a swfList - learn them separately, perhaps even as virtual objects mapped to these classes. If all else fails, that is.
Were you able to arrive at any workarounds for your issue. I am also having the same issue where SwFCombo box are getting recognized as SwfObjects in Summit Application by QTP 11. All other objects are getting recognized as expected.