Misleading notes on IfcVirtualElement

> Virtual elements are usually not displayed and do not have quantities, associated materials, and other measures.

The "associated materials" part is true. That's realized by the rule **IfcRelAssociatesMaterial.NoVoidElement** *The material information must not be associated to a subtraction feature (such as an opening) or to a virtual element*. But why wouldn't it have quantities or "other measures". Seems very relevant to have area measures for all usecases: imaginary boundary, provision for voids, clearance space.

No file or test is named. Start by reviewing the IfcVirtualElement notes and the cited IfcRelAssociatesMaterial.NoVoidElement rule in the IFC4.x specification, then check how quantities and other measures are described for virtual elements. Done means the notes accurately distinguish material restrictions from claims about quantities and measures.

Written by the indexing model from the issue text.