I did up an example .map file to illustrate.
The Slope and Aspect was calculated and stored with the Elevation from a Query derived from the lidar elevation. This let me link two surfaces to give illustration and keep file size down. I used a window parameter of 5 (11x11 spatial pixels around each calculated both for slope and aspect to smooth some of the noise.)
I generated a 100m grid and created them onto a drawing. I edited the grid drawing's Table to allow for aspect, slope, and height keeping the data type the same. This allowed me to use the Drawing - Transfer Heights... menu to assign the aspect, slope, and height to the points. I didn't really need the elevation to get transfered but brought it along. Then a couple of thematic changes to the points style to use these new columns to represent the slope as magnitude of arrow, and the aspect to show direction. One caveat, I manually changed the negative calculated aspect values in the grid drawing to cardinal direction by adding 360 to those <0deg.
To make a denser grid is almost trivial as the procedure is the same. To add further refinement of the aspect, slope (including the cardinal direction change) this can also be done in the query. There may be other ways to tackle this.
The data is a subset of the Douglas County, KS, USA lidar data at 2m resolution.
I hope this gives you some ideas that may help your project.