PDFParser Conflict Resolution

[Cary L. Schofield]

I have a signed document that is getting parsed incorrectly.
Using PDFParser the document form is missing all fields and I can't get 
to the signature fields.
Using NonSequentialPDFParser I can get to the signature fields but the 
signed data appears to have been corrupted.

I was able to determine that the form was being replaced or corrupted 
during conflict resolution.

I solved the problem by patching PDFParser.ConflictObj to ignore an 
object in the conflict list when the existing object (from the object 
pool) is a direct object.

I know I should do the research, but was hoping someone would already 
know if the patch is reasonable or likely to cause more/other problems.

Thanks