I thought this was such a good idea that I have started adding it to my own custom report.
One minor disadvantage of the way the report definitions work is that you have to add a lot of fields, using a tiny space in the editor. For example, the maximum number of spouses per individual in my main project is four, so that is eight separate fields to list both spouse and marriage details separately, but at least it only has to be done once.

- Capture.PNG (10.51 KiB) Viewed 1360 times
There is one minor curiosity in how FH treats missing data. In this example from the Sample Project, Spouse is defined with a data reference for the name, and the LifeDates() function for their dates, while Marriage is defined using two separate data references. In both case, the parentheses themselves are entered explicitly as character data.
If there are no dates for the spouse, FH is smart enough to realise that the LifeDates() function does not report anything, so it omits the parentheses automatically. However, if the marriage location is unknown, it keeps the blank parentheses, reporting it as below.

- Capture2.PNG (1.56 KiB) Viewed 1356 times
Presumably it is a subtle difference in how FH treats blank data from data references and functions. Perhaps it can be tidied up with more exotic coding, but it's still a difference that could catch people out.