Currently the costing framework when asked to cost a subtree of nodes (as opposed to just a single node), relies on the nodeCEMap structure which lists the individual cardinality estimates of the nodes, as the entire subtree is in the same group (not shredded). The goal of this task is (optionally) save the nodeCEMap on the best result of the memo and add ability to explain it.