anchor.diff:  <2> Each profile contains a section which holds details about the query execution
   <3> Each profile has a single time representing the cumulative rewrite time
   <4> Each profile also contains a section about the Lucene Collectors which run the search
  +<5> Each profile contains a section which holds the details about the aggregation execution
   
   Because a search request may be executed against one or more shards in an index, and a search may cover
   one or more indices, the top level element in the profile response is an array of `shard` objects.
  
positive.code:     This records the time taken to score a particular document via it's Scorer
  
  
  === `collectors` Section
  
  The Collectors portion of the response shows high-level execution details. Lucene works by defining a "Collector"
  which is responsible for coordinating the traversal, scoring and collection of matching documents.  Collectors
  
negative.code: 
  
  
  ==== `rewrite` Section
  
  All queries in Lucene undergo a "rewriting" process.  A query (and its sub-queries) may be rewritten one or
  more times, and the process continues until the query stops changing.  This process allows Lucene to perform
  