Thank you for your interest in Aspose.Word.
Good point. Aspose.Word object model provides classes for most of the Word document elements such as sections, paragraphs, tables, and many others. We also recently exposed the Field class which represents a MS Word field - but due to some reason the functionality of this class is currently limited and it does not allow reading field code and result. We will improve it later so it will be applicable for this purpose.
At the moment, you should implement your own logic to select fields from the document and read their contents. As you might know, a Word field normally contains of three parts - field start, field separator, and field end. In the Aspose.Word API, these objects are represented by the FieldStart, FieldSeparator, and FieldEnd classes, respectively. Field code is normally represented by a sequence of text runs enclosed between field start and field separator; field result is also a sequence of text runs enclosed between field separator and field end.
Until the Field class gets fully functional, you have to select field starts from the document and move through their siblings (nodes located at the same level) until the field end is met. We have a ready code sample that uses the mentioned approach to make it easier to work with hyperlinks in a document (hyperlinks are actually fields whose field code represents the hyperlink target and field result represents the hyperlink name). Take a look how the Hyperlink class works, pay special attention to its constructor where the field nodes are scanned to extract the code and result:
Feel free to post your further questions here.
Sorry for the delay, looking at this right now.
Please zip your document and attach here and I will see how Word count of fields is different from ours.